Endpoint computing device multi-network slice utilization system

ABSTRACT

An endpoint computing device multi-network slice utilization system includes a RAN system coupled to a core network system that allocates network slices and makes each of them available for use in wireless communications. An endpoint computing device includes applications and operates, for each of its applications, to detect that application, determine a networking connectivity requirement for that application, and identify one of the network slices that is allocated by the core network system, available via the RAN system, and that satisfies the networking connectivity requirement for that application. The endpoint computing device then establishes a connection for each of its application with the one of the network slices that satisfies the networking connectivity requirement for that application, and exchanges communications via the RAN system and the core network system for that application using the one of the network slices that satisfies the networking connectivity requirement for that application.

BACKGROUND

The present disclosure relates generally to information handlingsystems, and more particularly to endpoint information handling systemscapable of utilizing multiple network slices.

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option available to users is information handling systems. Aninformation handling system generally processes, compiles, stores,and/or communicates information or data for business, personal, or otherpurposes thereby allowing users to take advantage of the value of theinformation. Because technology and information handling needs andrequirements vary between different users or applications, informationhandling systems may also vary regarding what information is handled,how the information is handled, how much information is processed,stored, or communicated, and how quickly and efficiently the informationmay be processed, stored, or communicated. The variations in informationhandling systems allow for information handling systems to be general orconfigured for a specific user or specific use such as financialtransaction processing, airline reservations, enterprise data storage,or global communications. In addition, information handling systems mayinclude a variety of hardware and software components that may beconfigured to process, store, and communicate information and mayinclude one or more computer systems, data storage systems, andnetworking systems.

Information handling systems such as, for example, laptop/notebookcomputing devices, tablet computing devices, mobile phones, Internet ofThings (IoT) computing devices, and/or other endpoint computing devicesknown in the art, often utilize wireless networks in order to enablemobility of those endpoint computing devices while exchanging data, aswell as to exchange data from remote locations. Wireless networkingtechnology has begun to transition from 4G millimeter wave (4G) wirelesstechnology to 5G millimeter wave (5G) wireless technology. Currentconventional 5G wireless technology includes a 5G core network systemthat is operated by a wireless provider (e.g., AT&T® Mobility ofAtlanta, Ga., United States; SPRINT® Corporation of Overland Park,Kans., United States; VERIZON® Wireless of New York, N.Y., UnitedStates; etc.), and that operates with a 5G Radio Access Network (RAN)system that includes cellular tower systems that operate to exchangewireless communications for the endpoint computing devices discussedabove.

One technique for exchanging the wireless communications by the 5G corenetwork system for the computing devices discussed above includes theuse of network slicing, which one of skill in the art will recognize isa network architecture that enables the multiplexing of virtualized andindependent logical networks on the same physical networkinfrastructure, with each network slice providing a network (e.g., aportion of the wireless spectrum available from the 5G core networksystem) with a particular networking characteristics via the 5G RAN toany of the endpoint computing devices. The 5G specification definesnetwork slicing to enable the scaling of the 5G core network systeminfrastructure to computing devices having particular connectivitymetrics, and tends to work well for “single-function” computing devicessuch as the IoT computing devices (e.g., IoT power meter devices)discussed above, autonomous driving computing device, factory automationcomputing devices, and/or other single-function endpoint computingdevices known in the art.

For example, such single-function endpoint computing devices tend torequire a particular networking connectivity requirement (e.g., a lowbandwidth, low latency networking connectivity requirement for an IoTpower meter device) for their provided functionality, and thus a networkslice may be allocated at the 5G core network system and provided viathe 5G RAN system to single-function endpoint computing devices withnetworking connectivity requirements that may be satisfied by thenetworking characteristics of that network slice. However, generalpurpose endpoint computing devices such as the laptop/notebook computingdevices, tablet computing devices, and mobile phones discussed aboveprovide multiple functions (e.g., via multiple applications or workloadsoperating on those general purpose endpoint computing devices), and thusthe conventional provisioning of a network slice with particularnetworking characteristics that satisfy a particular networkingconnectivity requirement to such general purpose endpoint computingdevices will often result in a networking connection that is non-optimalfor at least some of the functionality provided by the general purposeendpoint computing device (e.g., at least some of the applications orworkloads operating on the general purpose endpoint computing device.)

Accordingly, it would be desirable to provide an endpoint computingdevice network slice utilization system that addresses the issuesdiscussed above.

SUMMARY

According to one embodiment, an Information Handling System (IHS)includes a processing system; and a memory system that is coupled to theprocessing system and that includes instructions that, when executed bythe processing system, cause the processing system to provide a networkslice engine that is configured, for each of a plurality ofapplications, to: detect that application; determine a networkingconnectivity requirement for that application; identify one of aplurality of network slices that is allocated by a core network system,available via a Radio Access Network (RAN) system, and that satisfiesthe networking connectivity requirement for that application; establisha connection for that application with the one of the plurality ofnetwork slices that satisfies the networking connectivity requirementfor that application; and exchange communications via the RAN system andthe core network system for that application using the one of theplurality of network slices that satisfies the networking connectivityrequirement for that application.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic view illustrating an embodiment of an InformationHandling System (IHS).

FIG. 2 is a schematic view illustrating an embodiment of an endpointcomputing device multi-network slice utilization system.

FIG. 3 is a schematic view illustrating an embodiment of an endpointcomputing device that may be provided in the endpoint computing devicemulti-network slice utilization system of FIG. 2.

FIG. 4 is a flow chart illustrating an embodiment of a method forutilizing multiple network slices by an endpoint computing device.

FIG. 5 is a schematic view illustrating an embodiment of a conventionalendpoint computing device network slice utilization system.

FIG. 6A is a schematic view illustrating an embodiment of the endpointcomputing device multi-network slice utilization system of FIG. 2operating during the method of FIG. 4.

FIG. 6B is a schematic view illustrating an embodiment of the endpointcomputing device multi-network slice utilization system of FIG. 2operating during the method of FIG. 4.

FIG. 6C is a schematic view illustrating an embodiment of the endpointcomputing device multi-network slice utilization system of FIG. 2operating during the method of FIG. 4.

DETAILED DESCRIPTION

For purposes of this disclosure, an information handling system mayinclude any instrumentality or aggregate of instrumentalities operableto compute, calculate, determine, classify, process, transmit, receive,retrieve, originate, switch, store, display, communicate, manifest,detect, record, reproduce, handle, or utilize any form of information,intelligence, or data for business, scientific, control, or otherpurposes. For example, an information handling system may be a personalcomputer (e.g., desktop or laptop), tablet computer, mobile device(e.g., personal digital assistant (PDA) or smart phone), server (e.g.,blade server or rack server), a network storage device, or any othersuitable device and may vary in size, shape, performance, functionality,and price. The information handling system may include random accessmemory (RAM), one or more processing resources such as a centralprocessing unit (CPU) or hardware or software control logic, ROM, and/orother types of nonvolatile memory. Additional components of theinformation handling system may include one or more disk drives, one ormore network ports for communicating with external devices as well asvarious input and output (I/O) devices, such as a keyboard, a mouse,touchscreen and/or a video display. The information handling system mayalso include one or more buses operable to transmit communicationsbetween the various hardware components.

In one embodiment, IHS 100, FIG. 1, includes a processor 102, which isconnected to a bus 104. Bus 104 serves as a connection between processor102 and other components of IHS 100. An input device 106 is coupled toprocessor 102 to provide input to processor 102. Examples of inputdevices may include keyboards, touchscreens, pointing devices such asmouses, trackballs, and trackpads, and/or a variety of other inputdevices known in the art. Programs and data are stored on a mass storagedevice 108, which is coupled to processor 102. Examples of mass storagedevices may include hard discs, optical disks, magneto-optical discs,solid-state storage devices, and/or a variety other mass storage devicesknown in the art. IHS 100 further includes a display 110, which iscoupled to processor 102 by a video controller 112. A system memory 114is coupled to processor 102 to provide the processor with fast storageto facilitate execution of computer programs by processor 102. Examplesof system memory may include random access memory (RAM) devices such asdynamic RAM (DRAM), synchronous DRAM (SDRAM), solid state memorydevices, and/or a variety of other memory devices known in the art. Inan embodiment, a chassis 116 houses some or all of the components of IHS100. It should be understood that other buses and intermediate circuitscan be deployed between the components described above and processor 102to facilitate interconnection between the components and the processor102.

Referring now to FIG. 2, an embodiment of an endpoint computing devicemulti-network slice utilization system 200 is illustrated. In theillustrated embodiment, the endpoint computing device multi-networkslice utilization system 200 incudes a core network system 202. In anembodiment, the core network system 202 may be provided by the IHS 100discussed above with reference to FIG. 1, and/or may include some or allof the components of the IHS 100, and in specific examples may includeserver devices, switch devices, storage devices, and/or other corenetwork system components connected together to provide a 5G corenetwork system that may be operated by a wireless provider (e.g., AT&T®Mobility of Atlanta, Ga., United States; SPRINT® Corporation of OverlandPark, Kans., United States; VERIZON® Wireless of New York, N.Y., UnitedStates; etc.) and may include any combination of physical and/or virtualcomponents that are configured to provide 5G wireless communications.However, while illustrated and discussed as physical and/or virtualcomponents that provide 5G wireless communications, one of skill in theart in possession of the present disclosure will recognize that othercomponents and/or component configurations may be utilized in a corenetwork system to provide other wireless communications capabilities(e.g., 4G wireless communications) while remaining within the scope ofthe present disclosure as well.

In the illustrated embodiment, the endpoint computing devicemulti-network slice utilization system 200 also includes a Radio AccessNetwork (RAN) system 204. In an embodiment, the RAN system 204 may beprovided by the IHS 100 discussed above with reference to FIG. 1, and/ormay include some or all of the components of the IHS 100, and mayinclude radio/cellular towers, base stations, antennas, core networkinterface devices, and/or any other RAN subsystems that would beapparent to one of skill in the art in possession of the presentdisclosure. In a specific example, the RAN system 204 may be a 5G RANsystem including cellular towers that are configured to provide forwireless communications by endpoint computing devices utilizing networkslices/spectrum allocated by the 5G core network system discussed above.For example, the RAN system 204 may provide an orchestration layer forwireless communications between communication devices and cellulartowers, allowing wireless communications to then be exchanged by a RANcontroller in the RAN system 204 via a Software Defined Networking (SDN)switch device and a separate control-based interface, the separation ofwhich allows the RAN system 204 to be flexible and accommodate NetworkFunction Virtualization (NFV) techniques utilized in 5G communications.

Furthermore, the endpoint computing device multi-network sliceutilization system 200 also include a plurality of endpoint computingdevices 206 a, 206 b, 206 c, and up to 206 d, each of which may beprovided by the IHS 100 discussed above with reference to FIG. 1, and/ormay include some or all of the components of the IHS 100. In a specificexample, the endpoint computing devices 206 a-206 d may be provided bymobile phones, tablet computing devices, laptop/notebook computingdevices, IoT computing devices, and/or any other endpoint computingdevices that would be apparent to one of skill in the art in possessionof the present disclosure. However, while a specific endpoint computingdevice multi-network slice utilization system 200 has been illustratedand described, one of skill in the art in possession of the presentdisclosure will recognize that the endpoint computing devicemulti-network slice utilization system of the present disclosure mayinclude a variety of components and component configurations whileremaining within the scope of the present disclosure as well.

Referring now to FIG. 3, an embodiment of an endpoint computing device300 is illustrated that may provide any or all of the endpoint computingdevices 206 a-206 d discussed above with reference to FIG. 2. As such,the endpoint computing device 300 may be provided by the IHS 100discussed above with reference to FIG. 1 and/or may include some or allof the components of the IHS 100, and in specific examples may beprovided by mobile phones, tablet computing devices, laptop/notebookcomputing devices, IoT computing devices, and/or any other endpointcomputing devices that would be apparent to one of skill in the art inpossession of the present disclosure. Furthermore, while illustrated anddiscussed as an endpoint computing device 300, one of skill in the artin possession of the present disclosure will recognize that thefunctionality of the endpoint computing device 300 discussed below maybe provided by other devices that are configured to operate similarly asthe endpoint computing device 300 discussed below.

In the illustrated embodiment, the endpoint computing device 300includes a chassis 302 that houses the components of the endpointcomputing device 300, only some of which are illustrated below. Forexample, the chassis 302 may house a processing system (not illustrated,but which may include the processor 102 discussed above with referenceto FIG. 1) and a memory system (not illustrated, but which may includethe memory 114 discussed above with reference to FIG. 1) that is coupledto the processing system and that includes instructions that, whenexecuted by the processing system, cause the processing system toprovide a network slice engine 304 that is configured to perform thefunctionality of the network slice engines and/or computing devicesdiscussed below. Furthermore, the memory system may also includeinstructions that, when executed by the processing system, cause theprocessing system to provide an application engine 305 that isconfigured to provide any or all of the applications discussed below asoperating on the endpoint computing device 300.

The chassis 302 may also house a storage system (not illustrated, butwhich may include the storage 108 discussed above with reference toFIG. 1) that is coupled to the network slice engine 304 (e.g., via acoupling between the storage system and the processing system) and thatincludes a network slice database 306 that is configured to store any ofthe information utilized by the network slice engine 304 discussedbelow. The chassis 302 may also house a communication system 308 that iscoupled to the network slice engine 304 and the application engine 305(e.g., via a coupling between the communication system 308 and theprocessing system) and that may be provided by a Network InterfaceController (NIC), wireless communication systems (e.g., cellularwireless components (e.g., 5G cellular wireless components), BLUETOOTH®components, Near Field Communication (NFC) components, WiFi components,etc.), and/or any other communication components that would be apparentto one of skill in the art in possession of the present disclosure.However, while a specific endpoint computing device 300 has beenillustrated, one of skill in the art in possession of the presentdisclosure will recognize that endpoint computing devices (or otherdevices operating according to the teachings of the present disclosurein a manner similar to that described below for the endpoint computingdevice 300) may include a variety of components and/or componentconfigurations for providing conventional endpoint computing devicefunctionality, as well as the functionality discussed below, whileremaining within the scope of the present disclosure as well.

Referring now to FIG. 4, an embodiment of a method 400 for utilizingmultiple network slices for an endpoint computing device is illustrated.As discussed below, the systems and methods of the present disclosureprovide for the utilization of respective network slices for differentfunctionality (e.g., different applications, different workloads, etc.)provided on any particular endpoint computing device. For example, acore network system that is coupled to a RAN system may allocate aplurality of a network slices and make each of the plurality of networkslices available for use in wireless communications via the RAN system.An endpoint computing device may include first and second applicationsthat are configured to operate on the endpoint computing device, and theendpoint computing device may detect each of the first application andthe second application, determine a first networking connectivityrequirement for the first application, and determine a second networkingconnectivity requirement for the second application. The endpointcomputing device may then identify a first network slice that isallocated by the core network system, available via the RAN system, andthat satisfies the first networking connectivity requirement for thefirst application. The endpoint computing device may also identify asecond network slice that is allocated by the core network system,available via the RAN system, and that satisfies the second networkingconnectivity requirement for the second application. Then endpointcomputing device then establishes a first connection for the firstapplication with the first network slice, and establishes a secondconnection for the second application with the second network slice.Subsequently, the first application may exchange first communicationsvia the RAN system and the core network system using the first networkslice, and the second application may exchange second communications viathe RAN system and the core network system using the second networkslice. As such, network slicing is extended to general purpose endpointcomputing devices running applications (or workloads) with differentnetworking connectivity requirements by providing for the utilization ofa respective network slice by each of those applications, thusoptimizing the networking connectivity of the general purpose endpointcomputing device on a per-application/per-workload/per functionalitybasis.

With reference to FIG. 5, an embodiment of conventional endpointcomputing device network slicing functionality using the endpointcomputing device multi-network slice utilization system 200 of FIG. 2 isillustrated for purposes of discussion and to contrast the endpointcomputing device multi-network slice functionality of the presentdisclosure. As illustrated in FIG. 5, the core network system 202 (e.g.,a 5G core network system) may operate to allocate network slices andmake those network slices available to via the RAN system 204 (e.g., a5G RAN system) for use in wireless communications. For example, arrowsare provided within the core network system 202 in FIG. 5 to representportions of spectrum that are available to the core network system 202,including a spectrum portion 500, a spectrum portion 502, and a spectrumportion 504 in the illustrated embodiment.

Furthermore, the allocation of network slices and the making of thosenetwork slices available via the RAN system 204 for use in wirelesscommunications by the core network system 202 is illustrated in FIG. 5by arrows provided in the RAN system 204, and may include the corenetwork system 202 allocating a network slice 500 a from the spectrumportion 500 (as illustrated by the arrow between the spectrum portion500 and the network slice 500 a), allocating a network slice 502 a fromthe spectrum portion 502 (as illustrated by the arrow between thespectrum portion 502 and the network slice 502 a), and allocatingnetwork slices 504 a and 504 b from the spectrum portion 504 (asillustrated by the respective arrow between the spectrum portion 504 andthe network slices 504 a and 504 b). One of skill in the art inpossession of the present disclosure would recognize that the allocationof network slices by a core network system, and the making of thosenetwork slices available by the core network system via a RAN system,may include a variety of conventional operations, and thus is notdescribed herein in detail. Furthermore, one of skill in the art inpossession of the present disclosure will appreciate that each networkslice 500 a, 502 a, 504 a, and 504 b may provide particular networkingcharacteristics including particular data transmission latency,particular data transmission throughput/bandwidth, particular datatransmission reliability, other particular Quality of Service (QoS)characteristics, and/or other particular networking characteristics thatwould be apparent to one of skill in the art in possession of thepresent disclosure.

As also illustrated in FIG. 5, each of the endpoint computing devices206 a-206 d may then operate to connect to a respective network slice inorder to utilize that network slice for exchanging wirelesscommunications via the RAN system 204 and the core network system 202(i.e., wireless communications with other endpoint computing devicescoupled to the RAN system 204, other endpoint devices coupled to anetwork that is coupled to the core network system 202, etc.) One ofskill in the art in possession of the present disclosure would recognizethat the connection to a network slice by an endpoint computing device,and the exchange of communications via a RAN system and core networksystem by that endpoint computing device using that network slice, mayinclude a variety of conventional operations, and thus is not describedherein in detail. As discussed above, the conventional endpointcomputing device network slicing illustrated in FIG. 5 and describedabove tends to work well for “single-function” computing devices such asIoT computing devices (e.g., IoT power meter devices), autonomousdriving computing device, factory automation computing devices, and/orother single-function endpoint computing devices known in the art thatinclude particular networking connectivity requirements, as thenetworking characteristics of a single network slice to which anendpoint computing device conventionally connects do not substantiallychange during the networking session associated with that connection.

However, the conventional endpoint computing device network slicingillustrated in FIG. 5 and described above introduces inefficiencies whenutilized with general purpose endpoint computing devices such aslaptop/notebook computing devices, tablet computing devices, and mobilephones that provide multiple functions (e.g., via multiple applicationsoperating on those general purpose endpoint computing devices), as theconventional provisioning of a conventional network slice withnetworking characteristics that satisfy a particular networkingconnectivity requirement to such general purpose endpoint computingdevices will often result in a networking connection that is non-optimalfor at least some of the functionality provided by the general purposeendpoint computing device (e.g., at least some of the applications orworkloads operating on the general purpose endpoint computing device.)As described below, the endpoint computing device multi-network sliceutilization systems and methods of the present disclosure remedy suchinefficiencies by allowing multiple separate endpoint computing devicefunctionalities provided by a single endpoint computing device (e.g.,applications, workloads, etc.) to each connect to and utilize arespective network slice that includes networking characteristics thatsatisfy the networking connectivity requirements of that endpointcomputing device functionality.

The method 400 begins at block 402 where an endpoint computing devicedetects applications. In the specific example provided below, the method400 is described as being performed by the endpoint computing device 206a. However, one of skill in the art in possession of the presentdisclosure will appreciate that the method 400 may be performed by anyor all of the endpoint computing devices 206 a-206 d at the same (ordifferent) times while remaining within the scope of the presentdisclosure as well. In an embodiment, at block 402, the applicationengine(s) 305 in the endpoint computing device 206 a/300 may operate toprovide one or more applications for operation on the endpoint computingdevice 206 a/300. For example, at block 402, the application engine(s)305 in the endpoint computing device 206 a/300 may operate to provide avideo communication application, an audio communication application, avideo streaming application, an office productivity application, agaming application, and/or any other applications that would be apparentto one of skill in the art in possession of the present disclosure. Aswould be appreciated by one of skill in the art in possession of thepresent disclosure, the applications provided at block 402 may operateto provide (or be replaced by) workloads operating on the endpointcomputing device(s), as well as any other endpoint computing devicefunctionality that one of skill in the art in possession of the presentdisclosure would recognize that benefitting from the dedicated networkslices functionality described below.

As such, in an embodiment of block 402, the network slice engine 304 inthe endpoint computing device 206 a/300 may operate to detect theapplications provided by the application engine(s) 305. For example, atblock 402, the network slice engine 304 in the endpoint computing device206 a/300 may detect the applications provided by the applicationengine(s) 305 and operating on the endpoint computing device 206 a/300in response to the launching of those applications, in response torespective network connection requests received from those applications,and/or in response to any other application detection event that wouldbe apparent to one of skill in the art in possession of the presentdisclosure. As such, continuing with the specific example providedabove, at block 402, the network slice engine 304 in the endpointcomputing device 206 a/300 may detect a video communication application,an audio communication application, a video streaming application, anoffice productivity application, and/or a gaming application provided onthe endpoint computing device 206 a/300. However, while the method 400is described as detecting applications at block 402, one of skill in theart in possession of the present disclosure will appreciate howworkloads and/or other functionality provided on the endpoint computingdevice 206 a/300 may be detected at block 402 while remaining within thescope of the present disclosure as well.

The method 400 then proceeds to block 404 where the endpoint computingdevice determines networking connectivity requirements for the detectedapplications. In an embodiment, at block 404, the network slice engine304 in the endpoint computing device 206 a/300 may operate to determinea networking connectivity requirement for each of the applicationsdetected at block 402. In an embodiment, the determination of thenetworking connectivity requirements for an application by the networkslice engine 304 in the endpoint computing device 206 a/300 may includethe application engine 305, which is providing an application,transmitting the networking connectivity requirements for thatapplication to the network slice engine 304 (e.g., as IP headerinformation in a data packet); the network slice engine 304 retrievingthe networking connectivity requirements for an application (e.g., inresponse to the detection of that application) that may have beenpreviously determined and stored in the network slice database 306 fromthe network slice database 306; and/or via any other networkingconnectivity requirement determination technique that would be apparentto one of skill in the art in possession of the present disclosure.

Continuing with the specific example provided above, at block 404, thenetwork slice engine 304 in the endpoint computing device 206 a/300 mayoperate to determine networking connectivity requirements for a videocommunication application detected at block 402 that includes arelatively high bandwidth networking connectivity requirement, arelatively low latency networking connectivity requirement, and arelatively high reliability networking connectivity requirement.Similarly, at block 404, the network slice engine 304 in the endpointcomputing device 206 a/300 may operate to determine networkingconnectivity requirements for an audio communication applicationdetected at block 402 that includes a relatively low bandwidthnetworking connectivity requirement, a relatively low latency networkingconnectivity requirement, and a relatively high reliability networkingconnectivity requirements. Similarly, at block 404, the network sliceengine 304 in the endpoint computing device 206 a/300 may operate todetermine networking connectivity requirements for a video streamingapplication detected at block 402 that includes a relatively highbandwidth networking connectivity requirement, a relatively intermediatelatency networking connectivity requirement, and a relativelyintermediate reliability networking connectivity requirement.

Similarly, at block 404, the network slice engine 304 in the endpointcomputing device 206 a/300 may operate to determine networkingconnectivity requirements for an office productivity applicationdetected at block 402 that includes a relatively intermediate bandwidthnetworking connectivity requirement, a relatively low latency networkingconnectivity requirement, and a relatively low reliability networkingconnectivity requirements. Similarly, at block 404, the network sliceengine 304 in the endpoint computing device 206 a/300 may operate todetermine networking connectivity requirements for a gaming applicationdetected at block 402 that includes a relatively very high bandwidthnetworking connectivity requirement, a relatively very high latencynetworking connectivity requirement, and a relatively very highreliability networking connectivity requirement. However, while a fewspecific examples are provided, one of skill in the art in possession ofthe present disclosure will appreciate how different applications,workloads, and/or functionalities operating on and/or provided by anendpoint computing devices may include a variety of different networkingconnectivity requirements, and that any of those networking connectivityrequirements may be determined at block 404 while remaining within thescope of the present disclosure as well.

Furthermore, in different embodiments, any particular application,workload, and/or functionality operating on the endpoint computingdevice 206 a/300 may include multiple application subsystems, workloadsubsystems, and/or functionality subsystems that have differentnetworking connectivity requirements (e.g., an application operating onthe endpoint computing device 206 a/300 may include a first applicationsubsystem having a first networking connectivity requirement, a secondapplication subsystem having a second networking connectivityrequirement, and so on), and those applications subsystems, workloadsubsystems, and/or functionality subsystems may be detected at block 402and their different networking connectivity requirements determined atblock 404. Further still, in some embodiments, multiple applicationsoperating on the endpoint computing device 206 a/300 may include thesame networking connectivity requirement (or respective networkingconnectivity requirements that fall within a particular networkingconnectivity requirement range) and, as such, those applications may bedetected, the networking connectivity requirements of those applicationsmay be determined, and those applications may be grouped in anapplication container that is associated with networking connectivityrequirement (or networking connectivity requirement range) of thoseapplications. Yet, further still, while the grouping of applicationswith the same or similar networking connectivity requirements into anapplication container is described as being performed during the method400, the application containers discussed above as being associated withan networking connectivity requirement or networking connectivityrequirement range may be determined prior to the method 400, stored inthe network slice database 306, and identified at block 404 from thatnetwork slice database 306 while remaining within the scope of thepresent disclosure as well.

The method 400 then proceeds to block 406 where the endpoint computingdevice identifies network slices that satisfy the networkingconnectivity requirements for the detected applications. In anembodiment, at block 406, the network slice engine 304 in the endpointcomputing device 206 a/300 may operate to identify a respective networkslice that satisfies each networking connectivity requirement determinedfor each of the applications at block 404. With reference to FIG. 6A,the core network system 202 (e.g., a 5G core network system) may operateto allocate network slices and make those network slices available tovia the RAN system 204 (e.g., a 5G RAN system) for use in wirelesscommunications. For example, arrows are provided in the core networksystem 202 in FIG. 6A to represent portions of spectrum that isavailable to the core network system 202, including a spectrum portion600, a spectrum portion 602, and a spectrum portion 604 in theillustrated embodiment.

Furthermore, the allocation of network slices and the making of thosenetwork slices available via the RAN system 204 for use in wirelesscommunications by the core network system 202 is illustrated in FIG. 6Aby arrows provided in the RAN system 204, and may include the corenetwork system 202 allocating a network slice 600 a from the spectrumportion 600 (as illustrated by the arrow between the spectrum portion600 and the network slice 600 a), allocating a network slice 602 a fromthe spectrum portion 602 (as illustrated by the arrow between thespectrum portion 602 and the network slice 602 a), and allocatingnetwork slices 604 a and 604 b from the spectrum portion 604 (asillustrated by the respective arrow between the spectrum portion 604 andthe network slices 604 a and 604 b). One of skill in the art inpossession of the present disclosure would recognize that the allocationof network slices by a core network system, and the making of thosenetwork slices available by the core network system via a RAN system,may include a variety of conventional operations, and thus is notdescribed herein in detail. Furthermore, one of skill in the art inpossession of the present disclosure will appreciate that each networkslice 600 a, 602 a, 604 a, and 604 b may provide particular networkingcharacteristics including particular data transmission latency,particular data transmission throughput/bandwidth, particular datatransmission reliability, other particular QoS networkingcharacteristics, and/or other particular networking characteristics thatwould be apparent to one of skill in the art in possession of thepresent disclosure

In some embodiments, each network slice allocated by the core systemnetwork system 202 and made available via the RAN system 204 by the corenetwork system 202 may be configured to identify the particularnetworking characteristics provided by that network slice. For example,each of the network slices 500 a, 502 a, 504 a, and 504 b may beconfigured to advertise its networking characteristics such that thenetwork slice engine 304 in the endpoint computing device 206 a/300 mayidentify the networking characteristics of each network slice that isavailable for connection to the endpoint computing device 206 a/300.FIG. 6B illustrates how the network slice 600 a may advertise itsnetworking characteristics 606 to the endpoint computing device 206 a(illustrated via a dashed arrow in FIG. 6B), the network slice 602 a mayadvertise its networking characteristics 608 to the endpoint computingdevice 206 a (illustrated via a dashed arrow in FIG. 6B), the networkslice 604 a may advertise its networking characteristics 610 to theendpoint computing device 206 a (illustrated via a dashed arrow in FIG.6B), and the network slice 604 b may advertise its networkingcharacteristics 610 to the endpoint computing device 206 a (illustratedvia a dashed arrow in FIG. 6B). One of skill in the art in possession ofthe present disclosure will appreciate that the dashed arrows in FIG. 6Bmay indicate the retrieval of the networking characteristics 606, 608,610, and 612 by the network slice engine 304 in the endpoint computingdevice 206 a/300 via the network slice advertisements discussed above.In a specific example, any particular network slice may identify itsnetworking characteristics via a network slice identifier, a networkslice name, a network slice data traffic QoS (e.g., default/best effort,video streaming best effort, enterprise high priority, etc.), and/or acode (e.g., 0x00, 0x1A, 0X12, etc.).

As such, at block 406, the network slice engine 304 in the endpointcomputing device 206 a/300 may identify the latency networkingcharacteristics, the throughput/bandwidth networking characteristics,the reliability networking characteristics, other QoS networkingcharacteristics, and/or any other networking characteristics provided byeach of the network slices 600 a, 602 a, 604 a, and 604 b. Furthermore,while a particular technique for identifying networking characteristicsof a network slice have been described, one of skill in the art inpossession of the present disclosure will appreciate that othertechniques for identifying networking characteristics of a network slicemay fall within the scope of the present disclosure as well. In aspecific example, a RAN controller in the RAN system 204 may inform theendpoint computing device about the number of network slices availableto that endpoint computing device from the RAN system, and the QoSnetworking characteristics associated with each network slice, whichallows the endpoint computing device to associate the data trafficprovided by each application or workload operating on that endpointcomputing device with a network slice that satisfies its networkconnectivity requirements, as discussed below.

Thus, at block 406, the network slice engine 304 in the endpointcomputing device 206 a/300 may identify a respective one of the networkslices 206 a-206 d that includes networking characteristics that satisfythe networking connectivity requirements of each of the applicationsdetected at block 402. Continuing with the example provided above, atblock 406 the network slice engine 304 in the endpoint computing device206 a/300 may identify a network slice that includes networkingcharacteristics that satisfy the networking connectivity requirementsfor a video communication application detected at block 402 thatincludes a relatively high bandwidth networking connectivityrequirement, a relatively low latency networking connectivityrequirement, and a relatively high reliability networking connectivityrequirement. Similarly, at block 406 the network slice engine 304 in theendpoint computing device 206 a/300 may identify a network slice thatincludes networking characteristics that satisfy networking connectivityrequirements for an audio communication application detected at block402 that includes a relatively low bandwidth networking connectivityrequirement, a relatively low latency networking connectivityrequirement, and a relatively high reliability networking connectivityrequirements. Similarly, at block 406 the network slice engine 304 inthe endpoint computing device 206 a/300 may identify a network slicethat includes networking characteristics that satisfy determinenetworking connectivity requirements for a video streaming applicationdetected at block 402 that includes a relatively high bandwidthnetworking connectivity requirement, a relatively intermediate latencynetworking connectivity requirement, and a relatively intermediatereliability networking connectivity requirement.

Similarly, at block 406 the network slice engine 304 in the endpointcomputing device 206 a/300 may identify a network slice that includesnetworking characteristics that satisfy networking connectivityrequirements for an office productivity application detected at block402 that includes a relatively intermediate bandwidth networkingconnectivity requirement, a relatively low latency networkingconnectivity requirement, and a relatively low reliability networkingconnectivity requirements. Similarly, at block 406 the network sliceengine 304 in the endpoint computing device 206 a/300 may identify anetwork slice that includes networking characteristics that satisfynetworking connectivity requirements for a gaming application detectedat block 402 that includes a relatively very high bandwidth networkingconnectivity requirement, a relatively very high latency networkingconnectivity requirement, and a relatively very high reliabilitynetworking connectivity requirement.

Furthermore, in some embodiments, at block 406 the network slice engine304 in the endpoint computing device 206 a/300 may identify respectivenetwork slices that include respective networking characteristics thatsatisfy different networking connectivity requirements for respectivemultiple application subsystems, workload subsystems, and/orfunctionality subsystems included in an application, workload, orfunctionality (e.g., a first network slice including first networkingcharacteristics that satisfy a first networking connectivity requirementfor a first application subsystem included in an application operatingon the endpoint computing device 206 a/300, a second network sliceincluding second networking characteristics that satisfy a secondnetworking connectivity requirement for a second application subsystemincluded in that application operating on the endpoint computing device206 a/300, and so on). Further still, in some embodiments, at block 406the network slice engine 304 in the endpoint computing device 206 a/300may identify a network slice that includes networking characteristicsthat satisfy the same networking connectivity requirement (or anetworking connectivity requirement range) for multiple applicationsthat have been grouped in an application container as discussed above.

As will be appreciated by one of skill in the art in possession of thepresent disclosure, the identification of respective network slices thatinclude networking characteristics that satisfy the networkingconnectivity requirements of each application operating on the endpointcomputing device 206 a/300 may include, for each application with aparticular networking connectivity requirement, the identification of anetwork slice that includes networking characteristics that are closestto those networking connectivity requirements, that fall within somerange of those networking connectivity requirements, and/or that one ofskill in the art in possession of the present disclosure would recognizemake that network slice the most desirable of the network slices thatare available to the endpoint computing device 206 a/300 for providingthat connection for that application. Furthermore, one of skill in theart in possession of the present disclosure will appreciate thatsituations may arise in which no network slices are available thatinclude networking characteristics that satisfy the network connectivityrequirements of an application and, in such situations, the networkslice that includes networking characteristics that most closely satisfythe network connectivity requirements of that application may beidentified for providing the connection for that application.

In some embodiments, the network slice engine 304 in the endpointcomputing device 206 a/300 may be configured to request network sliceswith particular networking characteristics that satisfy the networkingconnectivity requirements of applications detected to block 402. Forexample, after determining the networking connectivity requirements foran application at block 404, the network slice engine 304 in theendpoint computing device 206 a/300 may transmit a network slice requestcommunication via the RAN system 204 to the core network system 202(e.g., via an available connection to the core network system 202 thatmay have been previously established using conventional techniquesand/or the techniques described herein), with that network slice requestcommunication providing a request to allocate a network slice havingnetworking characteristics that satisfy the network connectivityrequirements of the application, and make that network slice availablevia the RAN system 204. As such, the core network system 202 may receivethat network slice request and, in response, may allocate a networkslice having the requested network connectivity requirements, and makethat network slice available via the RAN system 204 so that the networkslice engine 304 in the endpoint computing device 206 a/300 may identifythat network slice at block 406.

The method 400 then proceeds to block 408 where the endpoint computingdevice establishes connections for the detected applications with therespective network slices identified for those applications. In anembodiment, at block 408, the network slice engine 304 in the endpointcomputing device 206 a/300 may operate to establish a respectiveconnection for each application operating on the endpoint computingdevice 206 a/300 with the network slice that was identified at block 406as including networking characteristics that satisfy the networkingconnectivity requirements of that application. For example, at block408, the network slice engine 304 in the endpoint computing device 206a/300 may, for each application for which it identified a network sliceat block 406, present that application as a virtual endpoint computingdevice in network slice connection communications exchanged with the RANsystem 204, with the network slice communications operating to establisha connection between that application and the network slice that wasidentified for that application at block 406. As will be appreciated byone of skill in the art in possession of the present disclosure, thenetwork slice communications and/or establishment of the connectionbetween the network slice and the application that is presented as avirtual endpoint computing device may be similar to conventional networkslice/physical endpoint device communications and/or connectionestablishment, with the exception of the application being presented asa virtual endpoint computing device in the network slice connectioncommunications and/or connection establishment, and thus are notdescribed herein in detail.

As such, with reference to FIG. 6C, at block 408, the network sliceengine 304 in the endpoint computing device 206 a/300 may establish aconnection 614 for a first application operating on the endpointcomputing device 206 a with the network slice 600 a that was identifiedas having networking characteristics that satisfy the networkingconnectivity requirements determined for the first application,establish a connection 616 for a second application operating on theendpoint computing device 206 a with the network slice 602 a that wasidentified as having networking characteristics that satisfy thenetworking connectivity requirements determined for the secondapplication, and establish a connection 618 for a third applicationoperating on the endpoint computing device 206 a with the network slice604 a that was identified as having networking characteristics thatsatisfy the networking connectivity requirements determined for thethird application. While not illustrated, as discussed above one ofskill in the art in possession of the present disclosure will appreciatethat connections with multiple network slices for each applicationoperating on any or all of the endpoint computing devices 206 b-206 cmay be established in a similar manner while remaining within the scopeof the present disclosure as well.

Furthermore, in some embodiments, at block 408 the network slice engine304 in the endpoint computing device 206 a/300 may establish connectionsfor respective multiple application subsystems, workload subsystems,and/or functionality subsystems included in an application, workload, orfunctionality with respective network slices that include respectivenetworking characteristics that satisfy their different networkingconnectivity requirements (e.g., establishing a first connection with afirst network slice including first networking characteristics thatsatisfy a first networking connectivity requirement for a firstapplication subsystem included in an application operating on theendpoint computing device 206 a/300, establishing a second connectionwith a second network slice including second networking characteristicsthat satisfy a second networking connectivity requirement for a secondapplication subsystem included in that application operating on theendpoint computing device 206 a/300, and so on). Further still, in someembodiments, at block 408 the network slice engine 304 in the endpointcomputing device 206 a/300 may establish a connection with a networkslice that includes networking characteristics that satisfy the samenetworking connectivity requirement (or a networking connectivityrequirement range) for multiple applications that have been grouped inan application container. As such, one of skill in the art in possessionof the present disclosure will appreciate that any single endpointcomputing device may appear to the RAN system 204 and/or the corenetwork system 202 as many (e.g., tens, hundreds, or more) endpointcomputing devices due to the many applications operating on that singleendpoint computing device being presented as respective virtual endpointcomputing devices.

The method 400 then proceeds to block 410 where the endpoint computingdevice exchanges communications for the detected applications using theidentified network slices. In an embodiment, at block 410,communications may be exchanged between for each application using theconnection established with its respective network slice that satisfiesits respective networking connectivity requirements. As such, withreference to FIG. 6C, at block 410, the network slice engine 304 in theendpoint computing device 206 a/300 may utilize its communication system308 to exchange communications via the connection 614 with the networkslice 600 a for the first application operating on the endpointcomputing device 206 a (e.g., with a device coupled to the RAN system204, a device coupled to the core network system 202 via a network,etc.), may utilize its communication system 308 to exchangecommunications via the connection 616 with the network slice 602 a forthe second application operating on the endpoint computing device 206 a(e.g., with a device coupled to the RAN system 204, a device coupled tothe core network system 202 via a network, etc.), and may utilize itscommunication system 308 to exchange communications via the connection618 with the network slice 602 a for the third application operating onthe endpoint computing device 206 a (e.g., with a device coupled to theRAN system 204, a device coupled to the core network system 202 via anetwork, etc.) As will be appreciated by one of skill in the art inpossession of the present disclosure, the exchange of communications viaa connection with a network slice at block 410 may be similar toconventional network slice communication exchanges, with the exceptionof that multiple applications operating on the endpoint computing device206 a/300 may be exchanging communications via their respectiveconnections with their respective network slices that each includerespective networking characteristics that satisfy the networkingconnectivity requirements of those applications. As discussed below,each of the network slices provided by the core network system 202 areisolated from each other and, as such, any application or workload thatis operating on an endpoint computing device and that is utilizing aparticular network slice will be unaware of the other networks availablevia the other network slices being utilized by other applications orworkloads operating on that same endpoint computing device.

Furthermore, in some embodiments, at block 408 the network slice engine304 in the endpoint computing device 206 a/300 may operate to exchangecommunications for respective multiple application subsystems, workloadsubsystems, and/or functionality subsystems included in an application,workload, or functionality via connections provided with respectivenetwork slices (e.g., exchanging communications via a first connectionwith a first network slice for a first application subsystem included inan application operating on the endpoint computing device 206 a/300,exchanging communications via a second connection with a second networkslice for a second application subsystem included in that applicationoperating on the endpoint computing device 206 a/300, and so on).Further still, in some embodiments, at block 408 the network sliceengine 304 in the endpoint computing device 206 a/300 may exchangecommunications via a connection with a network slice for multipleapplications that have been grouped in an application container asdiscussed above.

The method 400 then proceeds to decision block 412 where it isdetermined whether a detected application is unavailable. In anembodiment, at decision block 412, the network slice engine 304 in theendpoint computing device 206 a/300 may operate to determine whether anapplication for which a respective connection was established with arespective network slice has become unavailable. For example, anapplication, workload, or other functionality operating on the endpointcomputing device may complete, be shut down, and/or may otherwise becomeunavailable in a manner that does not utilize the network slice withwhich that application, workload, or other functionality was connectedat block 410. As such, the network slice engine 304 in the endpointcomputing device 206 a/300 may operate to continuously or periodicallyto monitor applications (or application subsystems in an application, orapplications grouped in an application container) for which a connectionwith a network slice was provided at block 408 to determine whether thatapplication (or application subsystem) has become unavailable or isotherwise not utilizing the network slice to which it was connected.However, while a specific technique for monitoring for the use of anetwork slice has been described, one of skill in the art in possessionof the present disclosure will appreciate that network slice utilizationmay be determined in a variety of other manners that will fall withinthe scope of the present disclosure as well.

If, at decision block 412, it is determined that no detectedapplications are unavailable, the method 400 returns to block 410. Assuch, in response to determining that each application (or applicationsubsystem in an application, or application grouped in an applicationcontainer) for which a connection with a network slice was establishedat block 408 is still utilizing that network slice, the method 400 mayloop to continue to exchange communications for applications using theconnections to their network slices at block 410, and monitor whetherany of those applications have become unavailable at decision block 412.If at decision block 406, it is determined that a detected applicationis not available, the method 400 proceeds to block 414 where theendpoint computing device ends the connection with the identifiednetwork slice for the unavailable detected application. In anembodiment, at block 414 and in response to determining that anapplication (or application subsystem in an application, or allapplications grouped in an application container) is no longer utilizinga connection to a network slice that was provided at block 408, thenetwork slice engine 304 in the endpoint computing device 206 a/300 mayend that connection with the network slice for that application (orapplication subsystem in an application, or application container), andrelease that network slice for use by other applications and/or endpointcomputing devices. As will be appreciated by one of skill in the art inpossession of the present disclosure, the ending of a connection with anetwork slice at block 414 may be similar to conventional connectionending operations, and thus is not described herein in detail. Themethod 400 may then loop to continue to exchange communications foravailable applications using the connections to their network slices atblock 410, monitor whether any of those applications have becomeunavailable at decision block 412, and end connections to network slicesthat are no longer being utilized.

In some embodiments, repeated performance of the method 400 may allowthe network slice engine 304 in the endpoint computing devices 300 toperform intelligent network slice operations based on learned behaviorof the endpoint computing device 300 and/or the applications providedthereon. For example, the network slice engine 304 in the endpointcomputing device 300 may monitor the use of applications on the endpointcomputing device 300, the time of such application use on the endpointcomputing device 300, locations of the endpoint computing device 300,and/or any other information that would be apparent to one of skill inthe art in possession of the present disclosure, and may subsequentlyutilize that information to reserve network slices that includenetworking characteristics that satisfy the networking connectivityrequirements of particular applications. As such, when an endpointcomputing device repeatedly operates a particular application at aparticular time and in a particular location that utilizes a particularnetwork slice that includes networking characteristics that satisfy itsnetworking connectivity requirements, the network slice engine 304 inthe endpoint computing device 300 may learn that behavior andsubsequently operate to reserve that network slice at the learnedreoccurring application use time for use by the learned application inthe learned location. However, while a specific intelligent networkslice operation is described, one of skill in the art in possession ofthe present disclosure will recognize that other intelligent networkslice operations may be performed that will fall within the scope of thepresent disclosure as well.

Thus, systems and methods have been described that provide for theutilization of respective network slices for different functionality(e.g., different applications, different workloads, etc.) provided onany particular endpoint computing device. For example, a 5G core networksystem that is coupled to a 5G RAN system may allocate a plurality of anetwork slices and make each of the plurality of network slicesavailable for use in wireless communications via the 5G RAN system. Anendpoint computing device may include first and second applications thatare configured to operate on the endpoint computing device, and theendpoint computing device may detect each of the first application andthe second application, determine a first networking connectivityrequirement for the first application, and determine a second networkingconnectivity requirement for the second application. The endpointcomputing device may then identify a first network slice that isallocated by the 5G core network system, available via the 5G RANsystem, and that includes networking characteristics that satisfy thefirst networking connectivity requirements for the first application.The endpoint computing device may also identify a second network slicethat is allocated by the 5G core network system, available via the 5GRAN system, and that includes networking characteristics that satisfythe second networking connectivity requirements for the secondapplication. The endpoint computing device then establishes a firstconnection for the first application with the first network slice, andestablishes a second connection for the second application with thesecond network slice. Subsequently, the first application may exchangefirst communications via the 5G RAN system and the 5G core networksystem using the first network slice, and the second application mayexchange second communications via the 5G RAN system and the 5G corenetwork system using the second network slice. As such, network slicingis extended to general purpose endpoint computing devices runningapplications (or workloads) with different networking connectivityrequirements by connecting each of those applications (or workloads) toa respective network slice with networking characteristics that satisfyits networking connectivity requirements, thus optimizing the networkingconnectivity of the general purpose endpoint computing device on aper-application/per-workload/per functionality basis

Although illustrative embodiments have been shown and described, a widerange of modification, change and substitution is contemplated in theforegoing disclosure and in some instances, some features of theembodiments may be employed without a corresponding use of otherfeatures. Accordingly, it is appropriate that the appended claims beconstrued broadly and in a manner consistent with the scope of theembodiments disclosed herein.

What is claimed is:
 1. An endpoint computing device multi-network sliceutilization system, comprising: a Radio Access Network (RAN) system; acore network system that is coupled to the RAN system and that isconfigured to allocate a plurality of a network slices and make each ofthe plurality of network slices available for use in wirelesscommunications via the RAN system; and an endpoint computing device thatincludes a plurality of applications that are configured to operate onthe endpoint computing device, wherein the endpoint computing device isconfigured, for each of the plurality of applications, to: detect thatapplication; determine a networking connectivity requirement for thatapplication; identify one of the plurality of network slices that isallocated by the core network system, available via the RAN system, andthat satisfies the networking connectivity requirement for thatapplication; establish a connection for that application with the one ofthe plurality of network slices that satisfies the networkingconnectivity requirement for that application; and exchangecommunications via the RAN system and the core network system for thatapplication using the one of the plurality of network slices thatsatisfies the networking connectivity requirement for that application.2. The system of claim 1, wherein the endpoint computing device isconfigured, for at least one of the plurality of applications, to:request the one of the plurality of network slices that satisfies thenetworking connectivity requirement for that at least one of theplurality of applications, and wherein the core network system isconfigured to allocate the one of the plurality of network slices thatsatisfies the networking connectivity requirement for that at least oneof the plurality of applications in response to the request, and makethe one of the plurality of network slices that satisfies the networkingconnectivity requirement for that at least one of the plurality ofapplications available for use in wireless communications via the RANsystem.
 3. The system of claim 1, wherein the endpoint computing deviceis configured, for each of the plurality of applications, to: determinethat application is no longer available and, in response, end theconnection for that application with the one of the plurality of networkslices that satisfies the networking connectivity requirement for thatapplication.
 4. The system of claim 1, wherein the endpoint computingdevice is configured, for each of the plurality of applications, to:present that application as a virtual endpoint computing device whenestablishing the connection for that application with the one of theplurality of network slices that satisfies the networking connectivityrequirement for that application.
 5. The system of claim 1, wherein theendpoint computing device is configured, for at least two of theplurality of applications, to: identify one of the plurality of networkslices that is allocated by the core network system, available via theRAN system, and that satisfies a container networking connectivityrequirement for a container that includes those at least two of theplurality of applications; establish a container connection for thecontainer that includes those at least two of the plurality ofapplications with the one of the plurality of network slices thatsatisfies the container networking connectivity requirement for thecontainer; and exchange communications via the RAN system and the corenetwork system for those at least two of the plurality of applicationsusing the one of the plurality of network slices that satisfies thecontainer networking connectivity requirement for the container.
 6. Thesystem of claim 1, wherein each of the plurality of network slicesincludes a portion of a wireless communication spectrum that isavailable to the core network system.
 7. An Information Handling System(IHS), comprising: a processing system; and a memory system that iscoupled to the processing system and that includes instructions that,when executed by the processing system, cause the processing system toprovide a network slice engine that is configured, for each of aplurality of applications, to: detect that application; determine anetworking connectivity requirement for that application; identify oneof a plurality of network slices that is allocated by a core networksystem, available via a Radio Access Network (RAN) system, and thatsatisfies the networking connectivity requirement for that application;establish a connection for that application with the one of theplurality of network slices that satisfies the networking connectivityrequirement for that application; and exchange communications via theRAN system and the core network system for that application using theone of the plurality of network slices that satisfies the networkingconnectivity requirement for that application.
 8. The IHS of claim 7,wherein network slice engine is configured, for at least one of theplurality of applications, to: request the one of the plurality ofnetwork slices that satisfies the networking connectivity requirementfor that at least one of the plurality of applications, and wherein thecore network system allocates the one of the plurality of network slicesthat satisfies the networking connectivity requirement for that at leastone of the plurality of applications in response to the request, andmakes the one of the plurality of network slices that satisfies thenetworking connectivity requirement for that at least one of theplurality of applications available for use in wireless communicationsvia the RAN system.
 9. The IHS of claim 7, wherein network slice engineis configured, for at least one of the plurality of applications, to:determine that application is no longer available and, in response, endthe connection for that application with the one of the plurality ofnetwork slices that satisfies the networking connectivity requirementfor that application.
 10. The IHS of claim 7, wherein network sliceengine is configured, for at least one of the plurality of applications,to: present that application as a virtual endpoint computing device whenestablishing the connection for that application with the one of theplurality of network slices that satisfies the networking connectivityrequirement for that application.
 11. The IHS of claim 7, whereinnetwork slice engine is configured, for at least two of the plurality ofapplications, to: identify one of the plurality of network slices thatis allocated by the core network system, available via the RAN system,and that satisfies a container networking connectivity requirement for acontainer that includes those at least two of the plurality ofapplications; establish a container connection for the container thatincludes those at least two of the plurality of applications with theone of the plurality of network slices that satisfies the containernetworking connectivity requirement for the container; and exchangecommunications via the RAN system and the core network system for thoseat least two of the plurality of applications using the one of theplurality of network slices that satisfies the container networkingconnectivity requirement for the container.
 12. The IHS of claim 7,wherein each of the plurality of network slices includes a portion of awireless communication spectrum that is available to the core networksystem.
 13. The IHS of claim 7, wherein at least one of the plurality ofapplications provides a workload having the networking connectivityrequirement for that application.
 14. A method for utilizing multiplenetwork slices by an endpoint computing device, comprising: detecting,by an endpoint computing device, each of a first application and asecond application operating on the endpoint computing device;determining, by the endpoint computing device, a first networkingconnectivity requirement for the first application and a secondnetworking connectivity requirement for the second application;identifying, by the endpoint computing device, a first network slicethat is allocated by a core network system, available via a Radio AccessNetwork (RAN) system, and that satisfies the first networkingconnectivity requirement for the first application; identifying, by theendpoint computing device, a second network slice that is allocated bythe core network system, available via the RAN system, and thatsatisfies the second networking connectivity requirement for the secondapplication; establishing, by the endpoint computing device, a firstconnection for the first application with the first network slice, and asecond connection for the second application with the second networkslice; and exchanging, by the endpoint computing device, firstcommunications via the RAN system and the core network system for thefirst application using the first network slice, and secondcommunications via the RAN system and the core network system for thesecond application using the second network slice.
 15. The method ofclaim 14, further comprising: requesting, by the endpoint computingdevice, the first network slice that satisfies the first networkingconnectivity requirement for the first application, wherein the corenetwork system allocates the first network slice in response to therequest, and makes the first network slice available for use in wirelesscommunications via the RAN system.
 16. The method of claim 14, furthercomprising: determining, by the endpoint computing device, that thefirst application is no longer available and, in response, ending theconnection for the first application with the first network slice. 17.The method of claim 14, further comprising: presenting, by the endpointcomputing device, the first application as a first virtual endpointcomputing device when establishing the first connection for the firstapplication with the first network slice; and presenting, by theendpoint computing device, the second application as a second virtualendpoint computing device when establishing the second connection forthe second application with the second network slice.
 18. The method ofclaim 14, further comprising: identifying, by the endpoint computingdevice, the first network slice that is allocated by the core networksystem, available via the RAN system, and that satisfies a containernetworking connectivity requirement for a container that includes thefirst application and at least one third application; establishing, bythe endpoint computing device, a container connection for the containerthat includes the first application and at least one third applicationwith the first network slice that satisfies the container networkingconnectivity requirement for the container; and exchangingcommunications via the RAN system and the core network system for thefirst application and at least one third application using the firstnetwork slice that satisfies the container networking connectivityrequirement for the container.
 19. The method of claim 14, wherein thefirst network slice includes a first portion of a wireless communicationspectrum that is available to the core network system, and the secondnetwork slice includes a second portion of the wireless communicationspectrum that is available to the core network system.
 20. The method ofclaim 14, wherein the first application provides a workload having thenetworking connectivity requirement for the first application.